The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: himanshupathak95 <[email protected]>
Co-authored-by: Mamaduka <[email protected]>
Co-authored-by: afercia <[email protected]>
Co-authored-by: juanfra <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

After the first test gets refined, it would be nice to add another test as @juanfra mentioned in #68853 (comment)
To my understanding, it would be basically: set only the text color to white and see if the contrastChecker warns against the default background color.

@himanshupathak95, thanks for refactoring. Left two minor notes. Let's add the test case @afercia mentioned and this should be good to merge.

I think we can just use test steps and test everything in a single test.

Hey @Mamaduka, The failing test is passing locally for me -

While I'm debugging this, could you please confirm if the tests are passing on your end whenever it's convenient for you?

Thanks, @himanshupathak95!

I'll try to have a look at e2e tests next week.

The Check white text on default background step fails for me locally. The screenshot from the test results artifacts suggests there is a problem with the contrast checker in the first place as it doesn't show the notice:

I tested again the Contrast checker and it seems that right after adding some text in a paragraph and setting the text color the first time, the contrast checker doesn't appear indeed. Animated GIF:

In a way, I guess this test failure surfaces a potential bug in the Contrast checker that should be double checked first.

Thanks for testing this @afercia. You're correct that the warning appears, but not always as it should -

Hm, for me, when running the Gutenberg wp-env, Twenty Twenty-One shows the Default color palette. It should show its own color palette. Not sure why.
Anyways, I can't reproduce the bug consistently but it seems to happen only with the Gutenberg wp-env and the Default palette.
I can't reproduce it when running the WordPress wp-env with Gutenberg installed as a plugin, and in this case Twenty Twenty-One shows the Theme color palette.